TwinTurbo.NET: Nissan 300ZX forum - '91 TT won't fire! All Help Appreciated!!!
People Seeking Info
 
   


     
Subject '91 TT won't fire! All Help Appreciated!!!
     
Posted by tytyisfly27 on February 26, 2013 at 6:28 PM
  This message has been viewed 314 times.
     
     
Message Hey everyone!

This is my first post on TT.net. I've been a member for a few years now since I got my car, but I've never had a reason to post before since I could always find answers to all my questions somewhere in the forums. I've pulled/replaced my motor, done tons of plenum pulls, turbo upgrade etc.. and haven't had major issues yet.
Unfortunately my luck has run out, and I need all the help I can get.

Okay here's my scenario...
At the end of last summer, my car started to run and idle a bit rough. Since I know the old style injectors are famous for failure, I ohmed them up.. and sure enough it was time for them to be replaced.
I opted to go with the Nismo 740cc injectors with the early style adapter kit, and an EPROM from Z1. I got everything apart and put back together in a day or so, but when I went to start the car for the first time and it idled horribly. Convinced that I had pinched an o-ring or two, I pulled the plenum again, replaced the o-rings, changed the oil and tried again. Still the same result.

Thinking that perhaps the new EPROM was at fault. I called JWT and asked if it would be safe to swap in my old JWT EPROM that was tuned for my old style 555cc injectors just to check for problem with the new chip. I was told it would be no problem, so I went ahead, but to no avail. That same night I put the Z1 chip back in and didn't work on the car again for a few weeks.

When I finally went back to try and solve the problem for good, the car wouldn't start up at all.
I checked all the wiring to the injectors, pulled the CAS and listened for the injectors to fire and they did. I checked for spark on the first cylinder and it was fine. I replaced the PTU just to be sure. I checked all of the coil packs with my multimeter and all were fine. (I haven't checked for spark on individual cylinders since I know the PTU and coil packs are good).
I did a boost/vacuum leak test and everything was solid.
At this point if figured the only thing left to be at fault would be the fuel pump/controller, or the ECU.
I pulled the fuel hose off of the upper fuel rail, stuck it in a bottle, and turned the key to "on" to check fuel pressure. When I did, the pump primed.. but barely squirted any fuel out.
I called Joel at Z1, and told him about the problem I had been having, and asked if he thought that the fuel pump could be bad. By the description of what was going on, he seemed pretty sure that I needed a new fuel pump.
The same day, I ordered a new OEM fuel pump and fitting for a fuel pressure gauge, since I needed one anyways.

Well the pump came today, I swapped out the old one and still I have a very sad Z that won't start.
I am thinking I may have fried the ECU putting in the new chip or something, but it is still acting normal and throwing the same code 33(I had to cut the connector out of the harness and crimp a new sensor in for the time being... A shop had glued the connector together) and 34(short in the EFI harness) as usual. The car always ran just fine with these codes before, so I would assume that they are not at fault and that the ECU is functioning properly.

The only thing left to do, that I can think of, is swap the ECU, and do a compression test. I have a buddy that has a '93 NA, but I don't know how smart it would be to try to start a TT with 740cc injectors with an ECU programmed for 270's

I may have left some info out, as this problem has been ongoing for a few months now.
I'm no expert, but I have done just about everything you can do to a Z32 other than rebuild the motor, and this has got my completely stumped.

Any and all help is appreciated!

I'm gunna go back to the garage for a bit and give my car some dirty looks, and hope that it starts to feel guilty and fires up :)

     
Follow Ups  
     
Post a
Followup

You cannot reply to this message because you are not logged in.